-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(python): Update pyo3
and numpy
crates to version 0.23
#20111
base: main
Are you sure you want to change the base?
Conversation
97f1ea3
to
9bc2104
Compare
28d9b58
to
7843535
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #20111 +/- ##
==========================================
- Coverage 79.57% 79.56% -0.01%
==========================================
Files 1563 1563
Lines 217395 217418 +23
Branches 2472 2472
==========================================
- Hits 172986 172985 -1
- Misses 43841 43865 +24
Partials 568 568 ☔ View full report in Codecov by Sentry. |
pyo3
and numpy
crates to version 0.23
pyo3
and numpy
crates to version 0.23
pyo3
and numpy
crates to version 0.23
4144c9f
to
c4b62c3
Compare
@bschoenmaeckers Thanks for picking this up! Looks like the new PyO3 version causes deadlock somewhere - can you reproduce this locally? There's probably a clue in the migration guide somewhere on what could be causing this. |
Haven't had time to dig deeper today, but I could quite consistently reproduce this error locally with the following command.
|
Deadlock happens in the polars/crates/polars-python/src/on_startup.rs Lines 58 to 66 in bcfa7ec
|
b7c6361
to
db2410f
Compare
db2410f
to
1feac34
Compare
Ah (spent too many hours on this0, I also came to the conclusion that it is related to the warning. What I observe is that the GIL doesn't matter, but if I call |
Updated to latest pyo3 while ignoring most deprecations for now.